Alberto Garcia [Fri, 7 Feb 2025 13:40:10 +0000 (14:40 +0100)]
Use WTF_CPU_UNKNOWN when building for X32
Forwarded: no
WebKitGTK doesn't build on X32 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Fri, 7 Feb 2025 13:40:10 +0000 (14:40 +0100)]
Use WTF_CPU_UNKNOWN when building for riscv64
Bug: https://bugs.webkit.org/show_bug.cgi?id=271371
Forwarded: no
WebKitGTK doesn't build on riscv64 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Fri, 7 Feb 2025 13:40:10 +0000 (14:40 +0100)]
webkit2gtk (2.46.6-1) unstable; urgency=high
* New upstream release (Closes: #1092311).
* Refresh debian/patches/disable-nvidia-dmabuf.patch
* debian/copyright:
- Update copyright information of all files.
* debian/rules:
- Stop using -DWTF_CPU_ARM64_CORTEXA53=OFF, this was fixed upstream a
long time ago (WebKit bug #197192).
* debian/upstream/signing-key.asc:
- sq complains about multiple concatenated ASCII Armor blocks, so put
all keys in the same block.
Alberto Garcia [Thu, 19 Dec 2024 08:55:22 +0000 (09:55 +0100)]
Use WTF_CPU_UNKNOWN when building for X32
Forwarded: no
WebKitGTK doesn't build on X32 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Thu, 19 Dec 2024 08:55:22 +0000 (09:55 +0100)]
Use WTF_CPU_UNKNOWN when building for riscv64
Bug: https://bugs.webkit.org/show_bug.cgi?id=271371
Forwarded: no
WebKitGTK doesn't build on riscv64 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Wed, 27 Nov 2024 15:00:26 +0000 (16:00 +0100)]
Use WTF_CPU_UNKNOWN when building for X32
Forwarded: no
WebKitGTK doesn't build on X32 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Wed, 27 Nov 2024 15:00:26 +0000 (16:00 +0100)]
Use WTF_CPU_UNKNOWN when building for riscv64
Bug: https://bugs.webkit.org/show_bug.cgi?id=271371
Forwarded: no
WebKitGTK doesn't build on riscv64 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Wed, 27 Nov 2024 15:00:26 +0000 (16:00 +0100)]
webkit2gtk (2.46.4-1) unstable; urgency=high
* New upstream release.
* The WebKitGTK security advisory WSA-2024-0007 lists the following
security fixes in the latest versions of WebKitGTK:
- CVE-2024-44308, CVE-2024-44309 (fixed in 2.46.4).
Alberto Garcia [Wed, 30 Oct 2024 13:39:03 +0000 (14:39 +0100)]
Use WTF_CPU_UNKNOWN when building for X32
Forwarded: no
WebKitGTK doesn't build on X32 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Wed, 30 Oct 2024 13:39:03 +0000 (14:39 +0100)]
Use WTF_CPU_UNKNOWN when building for riscv64
Bug: https://bugs.webkit.org/show_bug.cgi?id=271371
Forwarded: no
WebKitGTK doesn't build on riscv64 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Wed, 23 Oct 2024 09:57:14 +0000 (11:57 +0200)]
Use WTF_CPU_UNKNOWN when building for X32
Forwarded: no
WebKitGTK doesn't build on X32 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Wed, 23 Oct 2024 09:57:14 +0000 (11:57 +0200)]
Use WTF_CPU_UNKNOWN when building for riscv64
Bug: https://bugs.webkit.org/show_bug.cgi?id=271371
Forwarded: no
WebKitGTK doesn't build on riscv64 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Wed, 23 Oct 2024 09:57:14 +0000 (11:57 +0200)]
webkit2gtk (2.46.2-1) unstable; urgency=medium
* New upstream release.
* Drop socket-monitor-crash.patch (included in this release).
* debian/control-common.in:
- The libwebkit*-dev packages are no longer Multi-Arch: same.
The s390x versions of the WebKit*.gir files are different due to a
change in a default value (WebKit bug #279220).
* debian/copyright:
- Update copyright information of all files.
* debian/rules:
- Stop disabling jpeg-xl in Ubuntu (Jeremy BÃcha).
- Remove the USE_PREBUILT_DOCS variable, we can always build the
documentation now.
- Fix build with -Nlibwebkitgtk-doc.
- Disable Skia on loong64 (Closes: #1082740).
Alberto Garcia [Thu, 17 Oct 2024 14:52:26 +0000 (16:52 +0200)]
Use WTF_CPU_UNKNOWN when building for X32
Forwarded: no
WebKitGTK doesn't build on X32 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Thu, 17 Oct 2024 14:52:26 +0000 (16:52 +0200)]
Use WTF_CPU_UNKNOWN when building for riscv64
Bug: https://bugs.webkit.org/show_bug.cgi?id=271371
Forwarded: no
WebKitGTK doesn't build on riscv64 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Thu, 17 Oct 2024 14:52:26 +0000 (16:52 +0200)]
webkit2gtk (2.46.1-2) unstable; urgency=medium
* Make the package Linux-only.
- debian/control*.in: Set Architecture: linux-any.
- debian/rules: Remove non-Linux quirks.
* debian/patches/socket-monitor-crash.patch:
- Fix crash due to a regression in 2.46.1 (WebKit bug #281495).
* debian/control.in:
- Require cmake 3.20.
Alberto Garcia [Thu, 19 Sep 2024 17:11:43 +0000 (19:11 +0200)]
Use WTF_CPU_UNKNOWN when building for X32
Forwarded: no
WebKitGTK doesn't build on X32 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Thu, 19 Sep 2024 17:11:43 +0000 (19:11 +0200)]
Use WTF_CPU_UNKNOWN when building for riscv64
Bug: https://bugs.webkit.org/show_bug.cgi?id=271371
Forwarded: no
WebKitGTK doesn't build on riscv64 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Thu, 19 Sep 2024 17:11:43 +0000 (19:11 +0200)]
webkit2gtk (2.46.0-2) unstable; urgency=medium
* debian/rules:
- Use -DUSE_SYSPROF_CAPTURE=OFF in unsupported arches.
- Enable bmalloc on armhf, using the system malloc is crashing the web
process (Closes: #1082148)
* debian/patches/fix-epiphany-ftbfs.patch:
- Disable webkit_settings_set_enable_2d_canvas_acceleration on
non-Skia builds. This fixes a FTBFS in epiphany-browser
(Closes: #1082149).
* debian/patches/disable-dmabuf-nvidia.patch:
- Bring back this patch (Closes: #1082139), see also #1039720.
* debian/patches/fix-bmalloc-armhf.patch:
- Fix the armhf build if bmalloc is enabled.
Alberto Garcia [Mon, 9 Sep 2024 12:22:28 +0000 (14:22 +0200)]
Use WTF_CPU_UNKNOWN when building for riscv64
Bug: https://bugs.webkit.org/show_bug.cgi?id=271371
Forwarded: no
WebKitGTK doesn't build on riscv64 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Mon, 9 Sep 2024 12:22:28 +0000 (14:22 +0200)]
Use WTF_CPU_UNKNOWN when building for X32
Forwarded: no
WebKitGTK doesn't build on X32 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
Alberto Garcia [Mon, 9 Sep 2024 12:22:28 +0000 (14:22 +0200)]
webkit2gtk (2.44.4-1) unstable; urgency=medium
* New upstream release.
* Drop fix-clang-build.patch and fix-webasm-crash.patch.
* debian/rules:
- Disable dh_dwz, it breaks the build in at least i386 and amd64
(see #1081000).
Alberto Garcia [Mon, 26 Aug 2024 13:24:02 +0000 (15:24 +0200)]
Use WTF_CPU_UNKNOWN when building for riscv64
Bug: https://bugs.webkit.org/show_bug.cgi?id=271371
Forwarded: no
WebKitGTK doesn't build on riscv64 even with the JIT disabled.
Treating the CPU as unknown is perhaps a bit severe, but it allows us
to get the build done until someone steps up to maintain this
properly.
===================================================================
projects / webkit2gtk.git / log